We've recently deployed Win7 Pro (64 and 32bit versions) in our enterprise. We noticed that some machines were double logging in. The user unlocks their session, the desktop starts to load and all of the sudden they have a login screen again. The second time is the charm. I've come across the KB977074 issue but we don't have that patch installed anywhere. Then there was the power settings fix - unchecking the "require a password on wakeup". This helped for all but two machines. The machines in question are runnig 64bit Win7 Pro. One is an Intel Core Duo and the other an Apple Mac Mini that's been wiped for Windows usage. They are located at a branch site which is on a 30+Mbps VPN so connecting to the DC is not really a problem. All other machines at the site are fine. With Win7's ability to switch networked users we've put it to the test and it works great except the two machines in question. Once someone is done with the machine they will lock the session until the next person performs a switch user to get into their sessions. This is where it asks for their credentials twice. None of the users have elevated privileges and there are many other machines with the exact same specs that do not have this problem. The logs show the person logging in, their session getting destroyed and logging back in - but the session is not truly destroyed as applications that were running before are still running. In addition there are no network errors showing on the switch in their environment. Any insight would be greatly appreciated. Oh, and both machines have been rebuilt from scratch with the same results. I found http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/83c1bae2-2335-4fbc-b299-5be2eb621389 to be very informative as well as http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/4bd97d58-1584-4d70-ab65-bbd66099483d. Thanks.

Hi, Thanks for posting in Microsoft TechNet forums. It seems that the issue is mainly caused by power settings. Besides unchecking the “Require a password on wakeup” setting, please also check the following items: 1. Check the following Group Policy setting, ensure it isn’t enabled. Computer Configuration\Administrative Templates\System\Power Management\Sleep settings\Require a Password When a Computer Wakes 2. Check if you enable a Screen Saver and check the box “On resume, display logon screen”, if you checked it, please uncheck the box. Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

1) This is disabled with our install scripts. It has fixed this issue for other machines, but not these two 2) I'll go through our GPO's and see if it is enabled anywhere. On the most part they will be at not configured, but I set both "Plugged In" and "On Battery" to disabled at the topmost policy for these two computers. I'm somewhat doubtful it is enabled anywhere because most of our policies are grandfathered from a 2K DC to the new 2K8 DC. Let's cross our fingers this works. Thanks.

Any progress? As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.